Devices, systems, and processes for authenticating devices

ABSTRACT

Devices, systems and process for authenticating devices are described. For at least one embodiment, a process for authenticating an IoT device with a hub to initiate an authenticated session, includes the operations of establishing an electronic data connection between an IoT device and a hub, sending an initial authentication signal including a cryptologic component and at least two perceptible components, receiving a responsive message secured by a cryptologic component and including a selection of at least one of the at least two perceptible components, determining whether the selection includes the identifying perceptible component, and establishing an authenticated session between the hub and the IoT device, if the result of the determining step is affirmative.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/853,329, filed on Dec. 22, 2017, in the name ofinventor Nathan Sones, and entitled “Devices, Systems, and Processes forAuthenticating Device,” the entire contents of which are incorporatedherein by reference.

TECHNICAL FIELD

The technology described herein generally relates to devices, systems,and processes for authenticating devices for interconnection to one ormore networks. More specifically, the various embodiments disclosedgenerally relate to authenticating Internet-of-Things (IoT) devices forinterconnection to one or more networks via a hub.

BACKGROUND

With the explosion of interconnected devices, such as IoT devices andother peripheral devices (hereafter individually and collectively, “IoTdevices”), a need exists for reliable, secure and efficient mechanismsfor connecting such IoT devices to one or more network data sources orother data locations. Often today, standalone devices or similar“all-in-one” devices, such as smartphones, personal data assistants, andsimilar devices are used to connect IoT devices to networked datasources or other data locations. Per such standard approach, each IoTdevice is individually managed, configured, connected, and secured tothe “all-in-one” device (hereafter, a “primary device”). Technologiessuch as Bluetooth and others facilitate some of these tasks and allowprimary devices to have one or more IoT devices connected thereto. Yet,there remains a need for a simplified mechanism for interconnecting,using, authenticating, securing, and managing IoT devices.

Further, primary devices are often expensive, bulky, and present uniqueconcerns when one seeks to connect with IoT devices. By providingmultiple functions and often configured as catch-all device, primarydevices often present unique concerns with size, disruption to dailyroutines, power concerns, security concerns, and other concerns. Theseconcerns of limit a primary device's capabilities to those supported bya given make, model, or version of a device. Often one is stuck with thebuilt-in features, such as cameras, processors, and others that prohibitadaptation of a primary device to unique needs, uses, or wants.

Further, protocols for connecting primary devices and IoT devices oftenvary by both the primary device and the IoT device. These protocolsoften involve the use of varying authentication processes, includingauthentication processes requiring the participation of third parties.Each IoT device user may also be required to know and use uniquepasswords, protocols, or other features that present obstacles to theeasy use of IoT devices with networked data sources or data locations.These concerns and others present unneeded challenges to use andintegration of IoT devices in everyday use, as a user is often tied totheir primary device for connectivity to data sources and datalocations. Accordingly, devices, systems, and processes are needed whichfacilitate the interconnection of IoT devices with data sources and/ordata locations without requiring the use of an “all-in-one” device.

SUMMARY

The various embodiments of the present disclosure relate in general todevices, systems, and processes for authenticating devices. Inaccordance with at least one embodiment of the present disclosure, aprocess for authenticating an IoT device with a hub to initiate anauthenticated session includes the operation of establishing anelectronic data connection between an IoT device and a hub. The processmay also include the operation of sending an initial authenticationsignal. For at least one embodiment, the initial authentication signalmay include a cryptologic component. For at least one embodiment, theinitial authentication signal may include at least two perceptiblecomponents. At least one of the at least two perceptible components mayinclude an identifying perceptible component. The process may alsoinclude receiving a responsive message. The responsive message may besecured prior to transmission by the IoT device. The responsive messagemay be secured by the cryptologic component. The responsive message mayinclude a selection of at least one of the at least two perceptiblecomponents. For at least one embodiment, the process may include theoperation of determining whether the selection includes an identifyingperceptible component. For at least one embodiment, when the selectionincludes the identifying perceptible component, the process may includethe operation of establishing an authenticated session between the huband the IoT device.

For at least one embodiment, a process for authenticating an IoT devicewith a hub may include the operation of establishing an electronic dataconnection by Bluetooth pairing an IoT device with a hub.

For at least one embodiment, a process for authenticating an IoT devicewith a hub may include use of a cryptologic component that includes apublic key of a public key—private key keychain. For at least oneembodiment, at least one of two perceptible components may include atleast one of an icon, a keyword, a sound, and a vibration. For at leastone embodiment, at least two perceptible components may be used andinclude at least two icons. For at least one embodiment, a responsivemessage may include a combination of a unique identifying icon and aunique identifying keyword. For at least one embodiment, a uniqueidentifying icon may be selectable from the at least two icons.

For at least one embodiment, a process for authenticating an IoT devicewith a hub may include use of a unique identifying keyword that iscommunicated to an IoT device in an initial authentication signal. Forat least one embodiment, the process may include receiving device useridentifying data. The device user identifying data may identify anintended user of an IoT device for a session. For at least oneembodiment, a process for authenticating an IoT device with a hub mayinclude determining whether an intended user is authorized for thesession. For at least one embodiment, the operation of determiningwhether an intended user is authorized for a session may include theoperation of contacting a user verification data service. For at leastone embodiment, user identifying data may be secured, prior totransmission by an IoT device, using a cryptologic component.

For at least one embodiment, a process for authenticating an IoT devicewith a hub may include use the operation of providing, during theauthenticated session, a communications link connecting an IoT devicewith a third-party service provider. For at least one embodiment, when acommunications link is established, data can be communicated between athird-party service provider and an IoT device. For at least oneembodiment, data may be communicated between a third-party serviceprovider via a device link between a hub and an IoT device. For at leastone embodiment, a hub link between a hub and a third-party serviceprovider may be utilized. For at least one embodiment, a device link maybe utilized during an authenticated session.

For at least one embodiment, a process for authenticating an IoT devicewith a hub may include communicating with a service provider. For atleast one embodiment, the service provider may be at least one of a webservices provider, a streaming service provider, and a data serviceprovider. For at least one embodiment, the service provider may be athird-party service provider.

For at least one embodiment, a process for authenticating an IoT devicewith a hub may include the operation of establishing a second hub linkbetween a hub and a second third-party service provider. For at leastone embodiment, the process may include establishing a second devicelink between an IoT device and a hub. For at least one embodiment, thesecond device link may facilitate a second authenticated session.

For at least one embodiment, a device for use in authenticating an IoTdevice with a hub may include use of a hub device configured for use inestablishing an authenticated session with an IoT device. For at leastone embodiment, a hub device may include a processor configured toexecute computer readable instructions for establishing an authenticatedsession between a device and an IoT device. For at least one embodiment,the hub device may include an input/output module. The input/outputmodule may be coupled to the processor. For at least one embodiment, thehub device may include a security module. The security module may becoupled to the processor. For at least one embodiment, the hub devicemay include a communications module. The communications module may becoupled to the processor. For at least one embodiment, the hub devicemay include a storage module. The storage module may be coupled to theprocessor. The storage module may be configured to store computerreadable instructions.

For at least one embodiment, a hub device may include computer readableinstructions for performing the operation of establishing an electronicdata connection between an IoT device and the hub device. The electronicdata connection may be established, at least in part, using acommunications module. For at least one embodiment, the instructions mayinclude those for performing the operation of sending, via thecommunications module, an initial authentication signal. For at leastone embodiment, the initial authentication signal may include acryptologic component generated by the security module. For at least oneembodiment, the initial authentication signal may include two or moreperceptible components. For at least one embodiment, the initialauthentication signal may include at least two perceptible components.For at least one embodiment, at least one of two or more perceptiblecomponents is an identifying perceptible component.

For at least one embodiment, a hub device may include computer readableinstructions for performing the operation of receiving a responsivemessage. The responsive message may be received using a communicationsmodule. The responsive message may be secured, prior to transmission bythe IoT device. A cryptologic component may be used to secure theresponsive message. For at least one embodiment, the responsive messagemay include a selection of at least one of the at least two perceptiblecomponents.

For at least one embodiment, a hub device may include computer readableinstructions for performing the operation of decrypting a responsivemessage. The responsive message may be decrypted using a securitymodule.

For at least one embodiment, a hub device may include computer readableinstructions for performing the operation of determining whether aselection includes an identifying perceptible component. For at leastone embodiment, a processor may be configured to perform the determiningoperation. For at least one embodiment, a hub device may includecomputer readable instructions for performing the operation ofestablishing an authenticated session between the hub device and the IoTdevice when a positive result is obtained from the determiningoperation. For at least one embodiment, a hub device may includecomputer readable instructions for performing the operation ofoutputting a humanly perceptible signal indicating the authenticatedsession is established when a positive result is obtained from thedetermining operation. The humanly perceptible signal may be outputusing an input/output module.

For at least one embodiment, a hub device may include a coupling moduleconfigured to couple an external device to the hub device. For at leastone embodiment, the coupling module may use at least one of physicalcoupling, magnetic coupling, inductive coupling, electrical coupling,and electro-optical coupling.

For at least one embodiment, a hub device may include at least one of apower source, a second input/output module, a mapping module, astreaming module, a second processing module, a second data storagemodule, a sensing module.

For at least one embodiment, a hub device may include a position module,coupled to the processor, and configured to determine a position of thehub device.

For at least one embodiment, a hub device may include a sensor module,coupled to the processor, and configured to monitor at least onebiometric for a user of the hub device and output at least one sensedsignal indicative of the monitored biometric.

For at least one embodiment, a hub device may include computer readableinstructions for performing the operation of receiving, from a sensormodule, at least one sensed signal. For at least one embodiment, a hubdevice may include computer readable instructions for performing theoperation of analyzing the at least one sensed signal for an emergencymedical condition. For at least one embodiment, a hub device may includecomputer readable instructions for performing the operation of detectingan emergency medical condition. For at least one embodiment, a hubdevice may include computer readable instructions for performing theoperation of establishing, using the communications module, acommunications link with a first-responder. For at least one embodiment,a hub device may include computer readable instructions for performingthe operation of communicating to a first-responder a current position,and at least one sensed signal.

For at least one embodiment, a non-transitory processor-readable mediumproviding processor-readable instructions configured to cause one ormore processors to execute an application program for use inestablishing an authenticated session between a hub and an IoT device isdescribed. For at least one embodiment, the processor-readableinstructions may include instructions for execution by a processor in anIoT device. For at least one embodiment, the instructions may includeestablishing an electronic data connection between the IoT device andthe hub. For at least one embodiment, the instructions may includereceiving from the hub an initial authentication signal. For at leastone embodiment, the initial authentication signal may include acryptologic component and at least two perceptible components. For atleast one embodiment, at least one of the at least two perceptiblecomponents is an identifying perceptible component.

For at least one embodiment, the processor-readable instructions mayinclude outputting a responsive message secured by the cryptologiccomponent. For at least one embodiment, the processor-readableinstructions may include a selection, by a user of the IoT device, of atleast one of the at least two perceptible components.

For at least one embodiment, the processor-readable instructions mayinclude requesting session data from at least one of the hub and athird-party service provider via the authenticated session between thehub and the IoT device. The session data may be requested upondetermining that the responsive message includes a selection of theidentifying perceptible component. The determining may be accomplishedby a hub.

For at least one embodiment, the processor-readable instructions mayinclude establishing an authenticated session between a hub and an IoTdevice. For at least one embodiment, session data may include dataprovided by at least one of a streaming video service provider, a webservice provider, and a data service provider.

BRIEF DESCRIPTION OF THE DRAWINGS

The features, aspects, advantages, functions, modules, and components ofthe devices, systems and methods provided by the various embodiments ofthe present disclosure are further disclosed herein regarding at leastone of the following descriptions and accompanying drawing figures. Inthe appended figures, similar components or elements of the same typemay have the same reference number and may include an additionalalphabetic designator, such as 108 a-108 n, and the like, wherein thealphabetic designator indicates that the components bearing the samereference number, e.g., 108, share common properties and/orcharacteristics. Further, various views of a component may bedistinguished by a first reference label followed by a dash and a secondreference label, wherein the second reference label is used for purposesof this description to designate a view of the component. When only thefirst reference label is used in the specification, the description isapplicable to any of the similar components and/or views having the samefirst reference number irrespective of any additional alphabeticdesignators or second reference labels, if any.

FIG. 1 is schematic representation of a system for connecting one ormore devices to a networked data source or other data location using ahub and in accordance with at least one embodiment of the presentdisclosure.

FIG. 2 is a schematic representation of a hub in accordance with atleast one embodiment of the present disclosure.

FIG. 3 is a flow chart depicting a process for interconnecting an IoTdevice with a hub in accordance with at least one embodiment of thepresent disclosure.

DETAILED DESCRIPTION

The various embodiments described herein are directed to devices,systems, and processes for providing connection by IoT devices to datasources and/or data locations, such as those reachable via one or moredata networks, without requiring the use of a primary device, such as asmartphone or PDA, by using a hub device. In accordance with at leastone embodiment of the present disclosure a hub device provides theminimal capabilities needed to facilitate connections of itself and IoTdevices to networked data sources and data locations. Acting as astand-alone device, the hub may be configured to provide connectivityfor high usage tasks, such as voice dialing, voice texting, interactionwith voice-based searching services, bio-medical reporting, emergencyservices, and others. Acting as a pass-through device, the hub may beconfigured to facilitate connectivity by one or more IoT devices withone or more networked data sources and/or data locations. Examples ofsuch connectivity may include the providing of streaming video servicesto an IoT device, where the IoT device provides the hardware andsoftware necessary to present videos and other audio/video content toone or more viewers and the hub facilitates connecting of the IoT devicewith a networked data streaming service. Acting as a pass-throughdevice, the hub may be paired with any desired IoT device to provide anydesired functionality. Thus, unlike today's primary devices, the hubdoes not require the functionality, in and by itself, to provide anydesired data, function, feature, service, or otherwise (hereafterindividually and collectively, “services”). Instead, such the datanetworking, authentication, and connectivity elements used in theproviding of services are facilitated by the hub, while the actualproviding of such services is facilitated by the IoT devicecommunicatively coupled to the hub.

As shown in FIG. 1, one embodiment of a system 100 for providingstand-alone and pass-through device capabilities includes a hub 102. Thehub 102 may be uniquely associated with and possessed by a person 104 (a“hub user”). The hub 102 may be configured in a form factor convenientto everyday wear, in practically any environmental condition, such as awatch, a pod (e.g., a shoe pod), a medallion, a badge (magnetically, orotherwise attached to a user's clothing), embedded in the person, orotherwise. When configured as a watch for at least one embodiment, thehub 102 may be configured for attachment to the user usinganti-bacterial materials, such as bamboo wrist bands and otherwise. Thehub 102 may be configured to provide stand-alone features and functions,such as the capability to provide voice services such as dialing,texting, searching, message playback, device control, and otherwise.Such voice services may be supported by connectivity by the hub 102 withone or more service providers, such as terrestrial services providers108, network service providers 110, satellite service providers 106, andother service providers. It is to be appreciated that the hub 102 may beconfigured in stand-alone mode to provider connectivity to one or moreservice providers, and thereby to other third-party service providers,data sources, data locations, or otherwise using any known or laterarising technologies and via one or more primary hub links 107 a-n. Suchprimary hub links 107 a-n may utilize any known or later arisingcommunications and/or networking technologies.

As further shown in FIG. 1, the system 100 may include one or more IoTdevices, such as one or more first IoT devices 118 a-n, one or moresecond IoT devices 120 a-n, one or more third IoT devices 122 a, andotherwise. An IoT device is typically a device that is not physicallyconnected to a hub for routine operations. For non-routine operations,such as maintenance, updating, and/or configuring of a hub, an IoTdevice may physically connected to a hub, if so desired for a givenembodiment. The system 100 may be configured for any given embodiment tosupport the use of any desired type of IoT device. Such IoT devices maybe configured for stand-alone use and/or use with one or morethird-party services, features, functions, data, or otherwise. Theparticularities of the hardware and software, features and functionssupported and provided by any given IoT device are limitless. In atleast one embodiment, the user of the IoT device, the “device user” isthe same as the hub user. In other embodiments, a device user may not bethe hub user. In one or more embodiments, the device user may rely uponpermissions from and/or rights associated with a hub user to use a givenIoT device. For example, a child desiring to access streaming videoservices may rely upon the permissions of an adult hub user to use suchservices.

The system 100 may also be configured to support the interconnectivityof an IoT device, via a hub 102, with one or more third-party serviceproviders. Non-limiting examples of such service providers may includeweb service providers 124, streaming service providers 126, and dataservice providers 128. The hub 102 provides connectivity between an IoTdevice and a service provider using one or more device communicationslinks (virtual “spokes”) between the IoT device and the hub 102, such asa 1^(st) spoke/device link 130 a-n, 2^(nd) spoke/device link 132 a-n,and Nth spoke/device link 134 a-n, and via one or more secondary hublinks 119 a-n, tertiary hub links 121 a-n, and one or more Nth hub links123 a.

For at least one embodiment, the hub 102 may be configured to act as acentral connectivity point with one or more virtual “spokes” connectingto one or more IoT devices. For at least one embodiment, the one or morevirtual “spokes” may exist as a data link between a given hub and one ormore IoT devices at a given time. The virtual spokes may be connected,configured, used by a hub and/or an IoT device that is withincommunications range of a corresponding hub. Spokes may be disconnected,disabled, or otherwise configured when a hub is not within range of agiven IoT device. Further, it is to be appreciated that thetechnologies, protocols, spectrum, and other elements used for a givenspoke/device link may be the same or different from one IoT device toanother. For example, an IoT device, such as the illustrative 2^(nd) IoTdevice 120 a-n used for streaming video services may be configured touse a high bandwidth spoke/device link, whereas a 1^(st) IoT device 118a-configured to provide access to one or more web services, such as anonline shopping service, a news feed service, or otherwise, may use alower bandwidth spoke/device link.

Likewise, the technologies, protocols, spectrum, and other elements of ahub link may be the same or may vary from those used to support a devicelink—as needed and/or desired to support the features and functionsprovided by a given IoT device. Further, such hub link characteristicsmay vary in view of the connectivity options available to a given hub,at a given, time, location, user preferences, data environment, andotherwise. As shown in FIG. 1, a given hub link 107/119/121/123 may beconfigured and/or configurable to support a service desired by the hubin support of one or more IoT devices.

For at least one embodiment, IoT devices may also be configured tosupport a hub 102 in its stand-alone device configuration. For example,a first IoT device 118 a-n may be configured to provide a display,mapping features and functions, and similar hardware and software usedto facilitate use of the hub 102 as a direction providing unit, forexample, a unit providing visual turn-by-turn directions while usingbuilt-in global positioning sensing/location sensing capabilities of ahub 102 so configured. Similarly, a second IoT device 120 a-n may beconfigured, when video streaming services are desired, to provide ahigher quality display while using primarily the pass-throughcapabilities of a hub 102. Likewise, an Nth IoT device 122 a-n may beconfigured to access data from a network data source or location, suchas data service provider 128. The IoT device may be configured to useboth the stand-alone capabilities and the pass-through capabilities of ahub 102. The stand-alone capabilities may include, for example, securitycapabilities, while the pass-through capabilities may include, forexample, the providing some or all of the data accessed from the dataservice provider 128 to the IoT device 122 a-n in any desired form,including encrypted, unencrypted, or otherwise. Thus, it is to beappreciated that a hub 102 may be configured to support any desiredcombination or use of a given hub's stand-alone and pass-throughcapabilities in support of the features and functions to be provided bya given IoT device, at a given time, and in any given environment.

As shown in FIG. 2 for at least one embodiment of the presentdisclosure, a hub 102 may include one or more of combinations of aprocessor 200, an input/output module 202, a power module 204, a storagemodule 206, a communications module 208, a sensor module 210, a securitymodule 212, a position module 214, and a coupling module 216. Othermodules or fewer modules may be used in other embodiments. The modulesmay be interconnected using known and/or later arising technologies. Theprocessor 200 may be any known or later arising processor capable ofproviding and/or supporting the features and functions of a hub asneeded for any given intended use of a hub and in accordance with one ormore of the various embodiments of the present disclosure. For at leastone non-limiting embodiment, the processor is configured as and/or hasthe capabilities of a 32-bit or 64-bit, multi-core ARM based processor.In at least one embodiment, the processor 200 is configured to supportboth stand-alone and pass-through capabilities.

For at least one embodiment, the processor 200 may be communicativelycoupled to at least one input/output module 202 configured to facilitateinterfacing with the user. The input/output module 202 may be configuredto support audible interfacing with the user. The input/output module202 may be configured to support audible interfacing using naturallanguage (e.g., commands and replies received and sent in a user'sdesired language), audible prompts (e.g., beeps, chimes, or the like),combinations of the foregoing, and otherwise. The input/output module202 may be configured to include known or later arising voicerecognition technology and/or to access such technologies from one ormore third-party service providers, such as via a hub link. Theinput/output module 202 may include tactile input devices, such asbuttons, capacitive or otherwise touch interfaces, or otherwise. Theinput/output module 202 may include tactile output interfaces, such aselements that cause the hub to vibrate. Vibration patterns, frequencies,or otherwise may be utilized to provide different signaling to the user.The input/output module 202 may be configured to include visual outputdevices, such as lights, visual displays, or otherwise. The input/outputmodule 202 may include features utilized to recognize a user, such asvoice recognition, facial recognition, finger print recognition,biometric recognition, or otherwise.

The input/output module 202 may include support for and/or be configuredto support other forms of user interface, including IoT devices 218supporting input/output messages between a user and a hub, such as theabove mentioned visual display provided by an IoT device in support ofdirection providing services. Such IoT devices 218 may becommunicatively coupled to the hub via a spoke/device link (for example,the first spoke/device link 130) and the communications module 208(described further below). It is to be appreciated that a stand-alonemode of operation and a pass-through mode of operation may executeindividually or substantially simultaneously, such as by use ofmulti-tasking, multi-threading, multi-core, or other processing hardwareand/or software technologies.

The input/output module 202 may include and/or be configured to supportone or more external devices 220 supporting input/output, sensing,position determining, communications, storage, or other features,functions or capabilities of a given hub. An external device 220 may becommunicatively coupled to the hub 102 via the coupling module 216 andan external device link 222 (each described further below). Examples ofexternal devices include, but are not limited to battery, digital watchface, analog watch face, touch screen, and camera. By use of IoT devices218 and/or external devices 220, such input/output features andfunctions may vary over time for any given hub. For at least onenon-limiting embodiment, the input/output module includes a microphone,a speaker and an input button. A depressing and/or holding of a buttonfor various time periods, sequences or otherwise may be supported by aninput/output module 202 and utilized by a user to control and/or changethe operating status of a hub. Voice commands may be used to changeand/or control the operating status of a hub. A shaking or suddenmovement of a hub, or a change in a measured characteristic of a user,as detected for example, by a sensor module 210, may be utilized by aninput/output module 202 to control and/or configure the operations of ahub. A change in location of a hub, for example, a movement of a hub apredetermined distance as determined for example by a position module214, may be utilized by an input/output module 202 to control and/orconfigure the operations of a hub.

The hub may be configured to support operations in any desiredenvironment, such as those arising in wet, dry, cold, hot, or otherwise.Accordingly, it is to be appreciated that the input/output module 202may be configured, for any given embodiment, to support desired inputand output features and functions for a hub and such features andfunctions may be augmented by use of IoT devices 218 and/or externaldevices 220.

As further shown in FIG. 2 and for at least one embodiment, a hub 102may include an internal power module 204. The power module 204 may beconfigured using any known or later arising technology. For at least oneembodiment, the power module 204 may include a battery having a desiredrating in amp-hours, output voltage, output current, or combinations ofthe foregoing. The power module 240 may be provided in a small orreduced size form factor designed to support an operating time of one ormore desired features or functions, with additional power being providedby an external device 220. The power module 204 may be recharged usingany known or later arising technology including, but not limited to,inductive charging. The power module 204 may be configured for use withpower sources provided in external devices 220. Such additional batterymay be used to recharge, augment, or provide power in addition to thepower module 204. An external device 220 may be configured to provideadditional power while also providing one or more other features orfunctions, such as the above-mentioned input/output functions and/orother features or functions desired for a given embodiment.

For example, an external device 220 configured to support streamingvideo services may include the providing of power to the hub during astreaming session by an external power source physically coupled to thehub. Such power may be provided using an external device link 222. Forat least one embodiment, an external device link 222 varies from a wireddevice link 224 with the former having a physical connection with a huband the latter having a remote connection, via a wire or data cable,with a hub. Either of the external device link 222 or the wired IoTdevice link 224 may be used to provide power and data signals to a hub.Further, an IoT device may be wirelessly linked to a hub using a devicelink 130/132/134. For example, a wired connection between an IoT deviceand a hub may be provided over an IoT device link 224, while a wirelessconnection may be provided over a device link 130/132/134. A given IoTdevice may be configured to support use of either type of link, wired orwireless. For at least one embodiment, the IoT device link 224 and thedevice link 130/132/134 may be configured as a single link, wired,wireless, inductive, or otherwise between a remote IoT device 218 and ahub 102. Accordingly, the links used between an IoT device and a hub arecollectively referred to herein as a “device link” with it beingappreciated that a wired device link may be configured to additionallyprovide power to a hub in addition to data. For at least one embodiment,an external device 220 may include a battery or power source.

As further shown in FIG. 2 and for at least one embodiment, a hub 102may include a storage module 206. The storage module 206 may beconfigured using any known or later arising data storage technologies.In at least one embodiment, the storage module 206 may be configuredusing flash memory technologies. For at least one embodiment, thestorage module 206 may be configured using micro-SD card technology. Thestorage module 206 may be configured to have any desired data storagesize, read/write speed, redundancy, or otherwise. The storage module 206may be configured to provide temporary/transient and/orpermanent/non-transient storage of one or more data sets. Such data setsmay include firmware and software instructions, and data for use inoperating the hub 102. Such data sets may include software instructionsconfigured for execution by the processor, another module of the hub102, an external device 220, an IoT device 218, or otherwise. Suchsoftware instructions provide computer executable operations thatfacilitate one or more features or functions of a hub, an IoT device, anexternal device, or otherwise. The storage module 206 may be configuredto operate in conjunction with network storage devices and servers, IoTdevices, external devices, and otherwise. For at least one embodiment,the storage module 206 may be configured to store one more data setsutilized to authenticate a hub user 104 with one or more providers.These and other data sets may be encrypted using known or later arisingtechnologies.

As further shown in FIG. 2 and for at least one embodiment, a hub 102may include a communications module 208. The communications module 208may be configured to utilize any known or later arising technology toestablish, maintain, and operate one or more hub links 107/119/121/123,device links 130/132/134, external device links 222, and/or wired IoTdevice links 224. Examples of technologies that may be utilized with oneor more embodiments include, but are not limited to, Bluetooth, ZigBee,Near Field Communications, WIFI, 3G, 4G, 5G, cellular, and others. Thecommunications module 208 may be configured to include one or more dataports for establishing connections between a hub and another device,such as a laptop computer. Such data ports may support any known orlater arising technologies, such as USB 2.0, USB 3.0, Ethernet,Firewire, HDMI, and others. The communications module 208 may beconfigured to support the transfer of data formatted using any desiredprotocol and at any desired data rates/speeds. The communications module208 may be connected to one or more antennas (not shown) to facilitatewireless data transfers. Such antenna may support short-rangetechnologies, such as 802.11a/c/g/n and others, and/or long-rangetechnologies, such as 4G, 5G, and others. The communications module 208may be configured to communicate signals using terrestrial systems,space based systems, and combinations thereof systems. For example, ahub 102 may be configured to receive GPS signals from a satellite.

As further shown in FIG. 2 and for at least one embodiment, a hub 102may include a sensor module 210. The sensor module 210 may include oneor more biometric, environmental, or other sensors. For at least oneembodiment, a hub 102 may be configured to directly sense one or more ofa user's biometrics, such as heartrate. Sensors may be configured forcontact with a user's skin facing. For at least one embodiment, a hubmay be configured to placement on a user's body to provide contact witha user's body to facilitate biometric sensing of one or more of suchuser's body functions. For at least one embodiment, a hub 102 may beconfigured to receive biometric signals, environmental signals, or othersensed signals (hereafter, individually and collectively “sensedsignals”), via the communications module 208, where such sensed signalsmay be obtained using an IoT device 218 and/or an external device 220.Such signals may be received using a wireless device link 130/132/134and/or a wired device link 224. A hub 102 may be configured to utilizeone or more sensed signals to monitor a user's current condition, suchas a heart rate, respiratory rate, blood pressure, or otherwise. A hub102 may be configured, based on such sensed signals, to take one or moreactions, such as notifying emergency services when a cardiac event issensed. A hub 102 may be configured to activate one or more componentsof an input/output module 202 based upon sensed signals. For example,when a user is having a cardiac event, as indicated by one or moresensed signals, a microphone and speaker may be activated, along with aGPS, and communications module, such that voice, location, heart rateand other information can be communicated to emergency responders. It isto be appreciated that any type of known or later arising sensortechnologies may be used in conjunction with one or more embodiments ofthe present disclosure. Such sensing technologies may be provided in ahub, in an external device and/or in an IoT device.

As further shown in FIG. 2 and for at least one embodiment, a hub 102may include a security module 212 configured to include hardware and/orsoftware which facilitates secure storage, processing, authentication,and communications of data between a hub 102, an IoT device 218, aservice provider, an external device 220, and otherwise. For at leastone embodiment, a security module 212 may be configured to support theuse of private and public encryption keys. Any known or later arisingdata security technologies may be used in and/or with security module212. Security module 212, in conjunction with storage module 206 may beconfigured to securely store a user's authentication credentials,preferences, passwords and otherwise used to access service providers.It is to be appreciated that the security module 212 may be configured,in conjunction with the sensor module 210, to “lock” or “unlock” (i.e.,provide access to or deny access to) one or more features and/orfunctions of a hub, an IoT device, an external device, and/or a serviceprovider based upon biometric signatures, such as heart rhythms, gaitprofiles, or otherwise.

As further shown in FIG. 2 and for at least one embodiment, a hub 102may include a position module 214. The position module 214 may includethe use of known or later arising positional, attitudinal, rotational,or other location and/or movement determining and/or sensingtechnologies. Non-limiting examples of such technologies include the useof GPS signals for position determinations. The use of wireless signaltriangulations for position determinations may be supported by positionmodule 214, where such wireless signal triangulations may arise usingpublic networks, private networks, or otherwise. Movement sensors, suchas accelerometers, rotational sensors, and others may be supported by aposition module 214. Such position, location and similar sensors beingidentified herein a “position sensors” and signals from such sensors as“position signals.” As discussed above, position signals from one ormore of such position sensors may be utilized to support one or morefeatures and/or functions of a hub 102, an IoT device, a serviceprovider, and/or an external device.

As further shown in FIG. 2 and for at least one embodiment, a hub 102may include a coupling module 216. The coupling module 216 may includeany desired type of connectivity devices for use in securing temporarilyor for any duration up to and including permanently, an external device220 to a hub 102. For at least one embodiment, the coupling module 218may facilitate magnetic coupling of an external device 220 to a hub 102.For at least one embodiment, the coupling module 218 may facilitate thephysical coupling, as distinguished from a data coupling, of an IoTdevice 218 to a hub. For at least one embodiment, the coupling module218 may facilitate physical coupling via the use of Velcro, fasteningsleeves, magnets, epoxies, or otherwise. For at least one embodiment,the coupling module 218 may facilitate both the physical coupling of anexternal device 220 and/or an IoT device 218 to a hub 102 as well as thecommunicative coupling of one or more of such devices. Suchcommunicative coupling may occur electrically, inductively,electro-optically, or otherwise. For at least one embodiment, thecoupling module 218 may be configured to provide electrical, physical,mechanical, and/or other isolation between a hub 102 and an externaldevice 220 or IoT device 218 coupled thereto.

It is to be appreciated that any given embodiment of a hub 102 mayinclude one or more of the above described modules and/or other modules,as desired to support a given individual or set of IoT devices while ina pass-through mode of operation, while providing a desired set of corefeatures and/or functions when operating in a stand-alone mode ofoperation.

As shown in FIG. 3, a process for establishing a connection between ahub 102 and an IoT device begins when a hub 102 enters the communicationrange of an IoT device 218 (Operation 300). It is to be appreciated thatthe hub 102, being commonly associated with a person, is typicallymobile. However, an IoT device may also be mobile relative to a thenstationary hub. For at least one embodiment, where a hub 102 isconfigured to communicate with IoT devices 218 using short-rangecommunications protocols, such as Bluetooth, the hub 102 and IoT device218 enter communications range when they are within a few dozen feet ofeach other. Further, it is to be appreciated that intermediate rangecommunications protocols, such as WIFI, may be used to establishcommunications between a hub 102 and an IoT device 218. Likewise, longerrange communications protocols, such as 4G and 5G, may be used between ahub 102 and an IoT device. Accordingly, when Operation 300 may occurwill typically depend upon one or more characteristics of a given IoTdevice and a given hub for a given implementation of an embodiment ofthe present disclosure.

Per Operation 302, upon a hub 102 and IoT device 218 entering (if notalready being present) within range, a communications link or connectionis established. It is to be appreciated that upon a first instance of ahub 102 and IoT device 218 begin within range, commonly known linkestablishment protocols may be used, such as Bluetooth pairingprotocols. Likewise, for a hub and IoT device that have been previouslyconnected, e.g., Bluetooth paired, such pairing protocols may or may notneed to be repeated. It is to be appreciated that a given hub 102 may bepaired, using one or more communications protocols, with one or moredevices at any given time. Likewise, for at least one embodiment, agiven IoT device may be paired with multiple hubs at any given time.

Per Operation 304, once the hub 102 and the IoT device 218 of interestat that time are “paired” or otherwise communicatively connected using aknown or later arising pairing protocol, the process proceeds with theIoT device, such as the Pt Device 118 a “listening” for anauthentication signal sent by a paired hub 102. That is, unlike manyprior art approaches where a device initiates authentication, per atleast one embodiment of the present disclosure, initiation of anauthentication process proceeds with a hub. It is to be appreciated thatper this process, as described further below, the user, via the hub,controls and initiates when an authentication and whether an eventualexchange of data by and between a hub and a given IoT device is tooccur.

Per Operation 306, upon receiving a user or other input to beginauthentication, hub authentication is activated. Activation of hubauthentication may occur based upon a depressing of an input button on ahub, based upon a biometric sensing, a positional sensing, a voicecommand, or otherwise. That is, activation of hub authentication mayoccur automatically, semi-automatically (e.g., based upon a sensedcondition), or manually upon a user action requesting suchauthentication activation.

Per Operation 308, the hub outputs an initial authentication signal. Inat least one embodiment, the initial authentication signal includes apublic key. In at least one embodiment, the public key is a transient ortemporary key having a pre-determined period for use. In at least oneembodiment, the public key is non-transient.

In at least one embodiment, the initial authentication signal may alsoinclude, in addition to at least the public key, data for use by thereceiving IoT device(s) to generate one or more icons for presentationto a user of the IoT device. The one or more icons may include a uniqueidentifying icon. The one or more icons may be any configuration ofgraphical or other characters, arranged in any desired order, that areassociable with a given hub. The identifying icon may have a temporaryassociation or a permanent association with a given hub. The outputtingof the identifying icon and other icon data, if any, may be based uponuser input arising at approximately the time of outputting or at anearlier time. The identifying icon may be presented to the hub userprior to output thereof by the hub in the initial authentication signal.The display need not be included in the hub device and instead may becommunicatively coupled thereto and provided by another device, such asby an external device or another IoT device which is alreadycommunicatively coupled to the hub.

In at least one embodiment, the initial authentication signal mayinclude, in addition to at least the public key, data for use by thereceiving IoT device(s) to generate one or more keywords, which mayinclude a unique identifying keyword, for presentation to a user of theIoT device. For at least one embodiment, the keywords may be anyconfiguration of alphanumeric characters. The keywords may be presentedin any language, typeface, character set, or combinations thereof. Thekeywords may be randomly generated by the hub. The identifying keywordmay be selected by or presented to the hub user prior to outputtingthereof by the hub in the initial authentication signal. In at least oneembodiment, the unique identifying keyword may not be included in theinitial authentication signal, but, is known to the IoT device user.

In at least one embodiment, the initial authentication signal mayinclude, in addition to at least the public key, data for use by thereceiving IoT device(s) to generate one or more sounds, which mayinclude an identifying sound, for presentation to a user of the IoTdevice. Such sound(s) may include one or more spoken words, sequences ofsounds, example, a Morris code pattern, or other audible sounds or soundpatterns. Such sounds may be presentable to a user of an IoT deviceusing a speaker, headphone, earbud, or other audible communicationtechnology provided by such IoT device or coupled thereof. The sound(s)may be presented in any language, sequence, or otherwise. The sound(s)may be randomly generated by the hub. The identifying sound(s) may beselected by the user prior to outputting thereof by the hub in theinitial authentication signal.

In at least one embodiment, the initial authentication signal mayinclude, in addition to at least the public key, data for use by thereceiving IoT device(s) to generate one or more vibrations, including anidentifying vibration, for presentation to a user of the IoT device.Such vibration(s) may include one or more sequences, for example, aMorris code sequence, or other humanly perceptible vibration patterns.Such vibrations may be presentable to a user of an IoT device usingknown technologies. The one or more vibration(s) may be randomlygenerated by the hub. The identifying vibration(s) may be selected byand/or presented to the hub user prior to outputting thereof by the hubin the initial authentication signal.

Accordingly, it is to be appreciated that an initial authenticationsignal includes a cryptologic component, such as a public key orotherwise, and one or more perceptible components, such as the abovediscussed icon(s), keyword(s), sounds, patterns, vibrations, orotherwise.

For at least one embodiment, the outputting of the initialauthentication signal may occur as a broadcast to any IoT device thenconnected to the hub. For at least one embodiment, the outputting of theinitial authentication signal may occur as a multicast or simulcast toonly those one or more IoT devices then communicatively coupled to thehub using one or more communications mediums. For example, an outputtingof the initial authentication signal may be multicast to those IoTdevices connected to the hub via near field communications, while suchauthentication signal is not output to those IoT devices connected tothe hub via Bluetooth, WIFI or other longer-range protocols. For atleast one embodiment, the outputting of the initial authenticationsignal may occur to only those one or more IoT devices supportingfeatures or functions then desired by a user. For example, a user mightinstruct, verbally or otherwise, his/her hub to activate a streamingvideo service. The hub may determine which then connected IoT devicesare both within a given range of the hub and can directly or indirectlyprovide the desired streaming video services, and further identify thecommunications protocols to use to output the initial authenticationsignal to such IoT devices.

Per Operation 310, IoT device(s), within range of the hub and using thecommunications protocol(s) used by the hub to output the initialauthentication signal, receive the initial authentication signal. It isto be appreciated that multiple IoT devices may receive the initialauthentication signal.

Per Operation 312, each IoT device receiving the initial authenticationsignal determines whether such device can process the cryptologiccomponent and present the perceptible component(s) to the IoT deviceuser. For example, an initial authentication signal including a publickeyword, an icon and a verbal password as its perceptible componentswould be disregarded by an IoT device not having audible outputcapabilities. If the IoT device does not have the necessary outputcapabilities, the process ends (Operation 313). If the IoT device hasthe necessary output capabilities, the process continues with Operation314. For at least one embodiment, an initial authentication signal mayspecify that how the perceptible components are output may vary by areceiving IoT device. For example, a keyword could be output visibly,audibly, by vibration and/or otherwise to an IoT device user.

Per Operation 314, for each IoT device receiving the initialauthentication signal and having the capabilities needed to present theperceptible components, the process continues with presenting theperceptible components to the device user. For at least one embodiment,the presented perceptible components may include an identifyingcomponent, such as an identifying icon, keyword, sound, vibration orcombination thereof, and other random/non-identifying perceptiblecomponents, such as other icons, keywords, sounds, vibrations orcombinations thereof.

Per Operation 316, the device user selects the corresponding identifyingperceptible component(s) and the IoT device communicates such selectionback to the hub. For at least one embodiment, this communicationutilizes the cryptologic component to encrypt the data and provide fordata security. For at least one embodiment, identification of two ormore perceptible components may be required, such as an identifying iconand an identifying password. It is to be appreciated that the deviceuser desirably knows which perceptible components are identifying andnon-identifying based upon such device user being either the same personas the hub user or in communication with the hub user by othermechanisms, such as by proximity, or by distant/remote connection (e.g.,by telephone).

Per Operation 317, an identification of a user of the IoT device mayoccur and may be communicated as device user identifying data to thehub. As shown by the dashed lines, this identification may be optionaland may occur prior to or after communication to the hub of the deviceuser's perceptible component selections. Identification of the deviceuser may include use of any known or later arising user identifiers suchas fingerprint, password, pin, pattern, or otherwise. The identificationof the device user may occur using the IoT device seeking authenticationwith the hub, using the hub itself, using a standalone device, such as apin input terminal, or otherwise. For at least one embodiment, thiscommunication utilizes the cryptologic component to encrypt the deviceuser identifying data and provide for data security.

Per Operation 318, the hub receives a responsive message from the IoTdevice. The responsive message including the device user's perceptiblecomponent selections and, when used, device user identifying data. Thehub decrypts the data provided in the received responsive message usingthe cryptologic components, such as a private key corresponding to thepublic key, and determines if such selections and user identifications,if any, are correct/as expected. It is to be appreciated that thedetermination of whether a user identification is correct/as expectedcan involve the use of pre-existing data stored and/or accessible by ahub and/or the use of user verification data services, such as thoseprovided by FACEBOOK, GOOGLE, APPLE, AMAZON and other service providers.

Per Operation 319, an optional number of re-entries/retries of eitherand/or both of selection of the identifying perceptible componentsand/or the device user identification data may be permitted. If so, thehub sends a retry message to the IoT devices. (Operation 321) If aproper selection and/or identification of the device user does not occurwithin a given number of re-entries/retries (which may be zero), the hubcommunicates a failure message to the IoT devices (Operation 323) andthe process ends (Operation 313).

Per Operation 320, when proper selections and, optional, device useridentification information is received by the hub, the process continueswith the hub communicating a success message back to the IoT device fromwhich the proper selections and identification originated.

Per Operation 322, secure, authenticated communications (“session data”)between the IoT device and the hub may occur using the cryptologiccomponent, such as a public key, communicated by the hub in the initialauthentication signal. The IoT device may be configured to store thecryptologic component for use during the then arising connection withthe hub. The session data may include any form of data, requests fordata, requests for connections with third party service providers, orotherwise. The session data may include and/or provide between theauthenticated IoT device and the hub, or vice versa, paymentinformation, personal information, user preferences, data protected byfurther data protection mechanisms, or otherwise. For at least oneembodiment, the session data may include a request by the authenticatedIoT device to establish a permanent connection with the hub. Such arequest for a permanent connection may be self-actuating such that uponthe hub coming into range of the authenticated IoT device, or viceversa, a secure connection is established using the cryptologiccomponent communicated in the initial authentication signal. It is to beappreciated that the authenticated IoT device may be configured toinclude secure data storage for the public key for such an embodiment.

For at least one embodiment, during a session (defined herein as thetime during which session data is communicated between a hub and anauthenticated IoT device), requests by the authenticated IoT device forthe hub to provide data to or perform one or more operations on behalfof the IoT device may require approval by the hub user. For example,upon receipt of a request by the authenticated IoT device for the hub toprovide certain data, the hub may be configured to notify the hub user,for example, via an audible tone or a vibration, and await approval bythe hub user of the request. The approval may occur, for example, by aspoken command from the hub user, by a button selection on the hub, by ashaking of the hub, or otherwise.

Per Operation 324, at some point in time the session will end. It is tobe appreciated, that the session may end upon completion of a desiredtransaction, for example, the end of a streaming video, after an elapseof time, after a period in which no further communications between theauthenticated IoT device and the hub are received, or otherwise.

Per Operation 326, at the end of the current session, a determination ismade by the hub as to whether the session is to be “permanent,” suchthat the public key may be used later, or “temporary.” If “temporary”,the cryptologic component, such as a public key, is erased in both thehub and the IoT device. Any later desired connections between the IoTdevice and the hub will then proceed anew at Operation 300. It thesession is deemed to be “permanent,” the process continues with the nexttime the hub and the authenticated IoT device are within range and theIoT device requests services from the hub, as per Operation 330. Thatis, upon the authenticated requesting services from the hub theconnection is again established, and communications proceed with theauthenticated IoT device using the cryptologic component communicated inthe initial authentication signal.

Per Operation 332, the process includes the verification that thecryptologic component, such as a public key, is still valid, and if so,the process continues with Operation 320. If the cryptologic componenthas expired or is not valid, the process continues with Operation 323.

Accordingly, it is to be appreciated that at least one embodiment of thepresent disclosure includes a process for authenticating an IoT devicewith a hub by use of a cryptologic component and a perceptiblecomponent, wherein each of these components are communicated by the hubto the IoT device and upon receipt of a valid responsive message backfrom an IoT device containing a selection of the perceptible component,the cryptologic component is utilized for further communications duringa session. It is also to be appreciated that for at least oneembodiment, a user identification may be utilized, in addition to theverification of a device user's selection of a perceptible component, toauthenticate a session. It is further to be appreciated, that theseprocesses may include the use of hardware and software, in the form ofone or more computer executable instructions, in each of an IoT deviceand a hub. Such computer executable instructions, cryptologic component,perceptible components, and other data may be stored in computerreadable mediums in a non-transient manner during a session, and forpermanent sessions, in a non-transient manner after a given session.

Although various embodiments of the claimed invention have beendescribed above with a certain degree of particularity, or withreference to one or more individual embodiments, those skilled in theart could make numerous alterations to the disclosed embodiments withoutdeparting from the spirit or scope of the claimed invention. The use ofthe terms “approximately” or “substantially” means that a value of anelement has a parameter that is expected to be close to a stated valueor position. However, as is well known in the art, there may be minorvariations that prevent the values from being exactly as stated.Accordingly, anticipated variances, such as 10% differences, arereasonable variances that a person having ordinary skill in the artwould expect and know are acceptable relative to a stated or ideal goalfor one or more embodiments of the present disclosure. It is also to beappreciated that the terms “top” and “bottom”, “left” and “right”, “up”or “down”, “first”, “second”, “next”, “last”, “before”, “after”, andother similar terms are used for description and ease of referencepurposes only and are not intended to be limiting to any orientation orconfiguration of any elements or sequences of operations for the variousembodiments of the present disclosure. Further, the terms “coupled”,“connected” or otherwise are not intended to limit such interactions andcommunication of signals between two or more devices, systems,components or otherwise to direct interactions; indirect couplings andconnections may also occur. Further, the terms “and” and “or” are notintended to be used in a limiting or expansive nature and cover anypossible range of combinations of elements and operations of anembodiment of the present disclosure. Other embodiments are thereforecontemplated. It is intended that all matter contained in the abovedescription and shown in the accompanying drawings shall be interpretedas illustrative only of embodiments and not limiting. Changes in detailor structure may be made without departing from the basic elements ofthe invention as defined in the following claims.

What is claimed is:
 1. A process comprising: at a first device,establishing a hub link with a second device; randomly generating atleast two perceptible components; wherein at least one of the at leasttwo perceptible components is an identifying perceptible component;sending, over the hub link, an initial authentication signal thatincludes the identifying perceptible component and a second perceptiblecomponent; receiving, over the hub link, a responsive message from thesecond device; determining whether the responsive message includes aselection of the identifying perceptible component; and when a result ofthe determining is affirmative, establishing an authenticated sessionover the hub link between the first device and the second device.
 2. Theprocess of claim 1, establishing a first connection between the firstdevice and the second device; wherein a first connection is establishedbefore the hub link is established; wherein the first connection isestablished using short range communications technology; and wherein thehub link is established using at least one of the short rangecommunications technology, an intermediate range communicationstechnology, and a long range communications technology.
 3. The processof claim 1, wherein the first device is a hub; and wherein the seconddevice is an Internet-of-things (IoT) device.
 4. The process of claim 1,wherein at least one of the at least two perceptible components includesat least one of a uniquely identifying sound, a uniquely identifyingsequence of two or more sounds, and a uniquely identifying Morris codepattern that includes two or more sounds.
 5. The process of claim 1,wherein the identifying perceptible component includes at least one of auniquely identifying vibration pattern, a uniquely identifying vibrationfrequency, and a uniquely identifying Morris code pattern that includestwo or more vibrations.
 6. The process of claim 1, further comprising:at the first device, receiving, from the second device and over the hublink, user data uniquely identifying an intended user of the seconddevice for the authenticated session; and determining whether theintended user is authorized for the authenticated session.
 7. Theprocess of claim 5, wherein the user data includes at least one of afingerprint, a password, a pin, and a pattern.
 8. The process of claim1, further comprising: at the first device, receiving, from the seconddevice and over the hub link, a cryptological component securing theresponsive message; and decrypting the responsive message based on thecryptological component.
 9. The process of claim 1, further comprising:before sending the authentication signal, presenting, by the firstdevice and in a humanly perceptible form, the identifying perceptiblecomponent to a user of the second device.
 10. The process of claim 1,further comprising: at the first device, communicatively couple, via anexternal hub link, the second device with a third device.
 11. Theprocess of claim 10, wherein the external hub link utilizes, in a firstpart, the hub link to connect the first device with the second deviceand, in a second part, a second hub link to connect the first devicewith the third device.
 12. The process of claim 11, wherein the thirddevice is at least one of data source, a satellite service provide, aterrestrial service provider, a streaming server, a web server, and aservice provider.
 13. A hub comprising: a hardware processor; a datastorage device; and a communications module operable using at least oneof a short-range communications technology, an intermediate rangecommunication technology; and a long range communications technology;and wherein the data storage device stores non-transitory hardwareprocessor executable instructions instructing the hub to: establish ahub link between the hub and a first device; randomly generate at leasttwo perceptible components; wherein at least one of the at least twoperceptible components is an identifying perceptible component; send, tothe first device and over the hub link, an initial authentication signalthat includes the identifying perceptible component and a secondperceptible component; receive, from the first device and over the hublink, a responsive message; determine whether the responsive messageincludes a selection of the identifying perceptible component; and whena result of the determining is affirmative, establish an authenticatedsession between the hub and the first device.
 14. The hub of claim 13,wherein at least one of the at least two perceptible components includesat least one of: a uniquely identifying sound; a uniquely identifyingsequence of two or more sounds; a uniquely identifying Morris codepattern that includes two or more sounds; a uniquely identifyingvibration pattern; a uniquely identifying vibration frequency; and auniquely identifying Morris code pattern that includes two or morevibrations.
 15. The hub of claim 14, wherein the non-transitory hardwareprocessor executable instructions further instruct the hardwareprocessor to: receive, from the first device and over the hub link, acryptological component securing the responsive message; and decrypt theresponsive message based on the cryptological component.
 16. The hub ofclaim 14, wherein the non-transitory hardware processor executableinstructions are further operable to instruct the hub to:communicatively couple, via an external hub link, the first device witha second device; wherein the external hub link utilizes, in a firstpart, the hub link connecting the first device with the hub and, in asecond part, a second hub link to connect the hub with the seconddevice; and wherein the second device is at least one of data source, asatellite service provider, a terrestrial service provider, a streamingserver, a web server, and an Internet service provider.
 17. The hub ofclaim 15, wherein the non-transitory hardware processor executableinstructions are further operable to instruct the hub to: receive fromthe first device and over the hub link, user data uniquely identifyingan intended user of the first device for the authenticated session; anddetermine whether the intended user is authorized for the authenticatedsession.
 18. A non-transitory computer processor readable data storagemedium comprising: hardware processor executable instructions which,when executed by a hardware processor in a hub, establish anauthenticated session between the hub and a first device by facilitatingoperations including: establishing, by the hub, a hub link with thefirst device; randomly generating, by the hub, at least two perceptiblecomponents; wherein at least one of the at least two perceptiblecomponents is an identifying perceptible component; sending, by the huband over the hub link, an initial authentication signal that includesthe identifying perceptible component and a second perceptiblecomponent; receiving by the hub, from the first device, and over the hublink a responsive message; determining, by the hub, whether theresponsive message includes a selection of the identifying perceptiblecomponent; and when a result of the determining is affirmative,establishing an authenticated session over the hub link between the huband the first device.
 19. The non-transitory computer processor readablemedium of claim 18, wherein the hardware processor executableinstructions further facilitate operations comprising: receiving fromthe first device and over the hub link, user data uniquely identifyingan intended user of the first device for the authenticated session; anddetermining whether the intended user is authorized for theauthenticated session.
 20. The non-transitory computer processorreadable medium of claim 18, wherein the hardware processor executableinstructions further facilitate operations comprising: communicativelycoupling the first device with at least one of data source, a satelliteservice provide, a terrestrial service provider, a streaming server, aweb server, and a service provider.